WebloginPE for Revo - Any thought's

Hi All

My name is Allan (allanb)

I am thinking of starting on a REVO version of WebloginPE.

Has anyone any thoughts or ideas on this

Would you be interested in helping or joining such a project

I am fairly new to this but have made a start by putting together a Version 1.3.2 Beta (should be ready soon).
I have tried to incorperate existing fixes etc. Am busy with XHTML validation and other minor problems.

I would be particularly interested in where you think this should take place.

My ideas :-

1. Using Google webloginpe existing repository with a new Revo branch.
2. Using New Google repository set up for WebloginRevo only.

--or any other ideas--

Comments and ideas please.

Not everyone has to code.
Good doc’s are vital.
Translators would be needed.

Lets try and make this better for all.

Regards
Allan

I think a new component should be created for Revo from scratch. TBH, I will not use or endorse WLPE for any reasons due to scalability and many other code issues. The code in Revo is so much different, such a component really needs to be re-examined from an architectural perspective.

Functionally, WLPE has some killer ideas and features indeed. However as Jason mentioned, it really chokes on itself when you get a couple thousand web users.

I’d love to see someone create a killer user-manager component for Revo that can be used on front-end applications. Note also that Revo doesn’t really have a distinction between user-types. Any user can have access to different contexts.

Thanks OpenGeek & rthrash.

I was also concerned with the WLPE structure.

After reading the Revo database tutorial I was also wondering how we would be able to let a parameter add extra tables and fields which could generate the required schema and mappings. This I think would be difficult to say the least.

I believe quite a few people are using WLPE.

I do not know how much of the code is used but I have found code that could just not work but maybe people were not using those functions.

Do we need some form of a survey to determine needs.

I am realy getting out of my depths here.

I must also say I have not found any documentation easy to read on Revo. Especially for those how don’t do this for a living. But maybe it’s just me.

I was hoping to follow in Mary’s footsteps and learn and try to give back what I have learnt in the way of tutorials.
I have learnt far more from Mary’s tutorials than the docs.

I hope to get some more replies for food for thought.

Keep them comming
Allan

Quote from: allanb at Mar 23, 2010, 01:29 PM

After reading the Revo database tutorial I was also wondering how we would be able to let a parameter add extra tables and fields could generate the required schema and mappings. This I think would be difficult to say the least.

Revo has a table where you can’t put your custom setting bult in (Setting tab).

I did use it for testing purpose and access it like so:



Which return the corresponding custom "test" setting value.
Maybe it can be useful to use this facility instead of another table?

Hi lossendale

The web_user_attributes database has 22 fields. These I could see being setup using schema as in tutorial as these are fixed.(I was going to start there using xPDO)

And the web_user_attributes extended database has as many fields as required I have seen about 10 I think.
These were the fields I was refering too in post

Please say if I am not seeing something.

Thanks
Allan

the table modx_user_attributes as 25 fields.
There is another table called modx_user_settings which have 7 fields: ’user’,’key’,’value’,’xtype’,’namespace’,’area’,’editedon’

It may be possible to use this table to developp a webloginPE like component for Revolution without the need to create another table by using this already existing table?

Hi lossendae

I was refering to the fact that the ’user’ gets to chose field names and types so existing or new table is not the point I was trying to say this would not be that easy with generating the schema maps etc.

And maybe at some time in the future just add new paramater to call and add even more fields.

Sorry to push the point. Maybe I am not clear in my remarks(English was my worst subject)

I was also wondering why WLPE chokes how can it be done better

This seems a much read post not many replies.

Regards
Allan

I was refering to the fact that the ’user’ gets to chose field names and types so existing or new table is not the point I was trying to say this would not be that easy with generating the schema maps etc.

If the table already exist you do not need to generate any maps files.

Since it’s a key => value table, you would be able to create new parameter on the fly.

I’m not saying that it is easy, i’m not capable to do it myself (for general purpose) and i might also be wrong or misunderstanding your point.

Hi lossendae

Sorry I am not understanding ’key’ concept will go do some research.

Still stuck with Revo terms.

Thanks anyway
Allan