On Pebble design

[Petre Maierean]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hello,

I'm reviewing the current design of Pebble in order to customize its page template for personal use. Not sure about how many developers are still on this list. Just wandering how many of you would be interested in participating in an initiative to modify the presentation tier of the application to make it more flexible for customization

I am thinking of replacing the current view and controller (DefaultHttpController + Actions + View) with Apache Struts + Tiles + Spring FW + JQuery.js. I would also add Hibernate for the model's persistence layer (as a more transactional oriented repository for user data and blog entries)

Anyways, I'd like to contribute the review result within a few days. This will be a PDF document, like a basic compendium with my findings on Pebble 2.6.2 . Maybe it should be part of the project, but not sure where to uploaded to though

regards,

Petre Maierean
http://www.linkedin.com/

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[James Roper-6]

Hi Peter,

I have considered moving to a new MVC framework for Pebble, but
haven't yet because I don't think there are any major gains to be had
from rewriting the 50 or so actions.  What exactly do you want to
customise?  In Pebble 2.6.x I've added the ability to plugin in
actions and views, have a look at
https://bitbucket.org/jroper/pebble-mobile-plugin to see how this can
be done.  Though it is hand rolled, the current MVC framework in
Pebble is incredibly fast and simple, it's one of the things that
contributes to the speed of Pebble starting up, and also ensures that
Pebbles size isn't massive.

I'm more of a Sitemesh fan than Tiles fan, Sitemesh allows some really
cool stuff especially when it comes to making things pluggable.

Moving to jQuery may be a good idea, I've had a chat with Olaf and he
has suggested YUI instead.  I'm not set on either one particularly.

I am definitely against moving to Hibernate, hibernate is slow and
overkill for Pebble, and will likely complicate Pebble setup, the
whole point of Pebble is for it to be lightweight and very quick to
setup and install.  Additionally, RDBMS is the wrong solution for
storage in a document oriented application like Pebble, a NoSQL
Document based solution would be much better, I am currently thinking
OrientDB as it is Java, lightweight, and embeddable.

Cheers,

James

On 15 June 2011 03:06, Petre Maierean <pgm66plus@...> wrote:

> Hello,
>
> I'm reviewing the current design of Pebble in order to customize its page
> template for personal use. Not sure about how many developers are still on
> this list. Just wandering how many of you would be interested in
> participating in an initiative to modify the presentation tier of the
> application to make it more flexible for customization
>
> I am thinking of replacing the current view and controller
> (DefaultHttpController + Actions + View) with Apache Struts + Tiles + Spring
> FW + JQuery.js. I would also add Hibernate for the model's persistence layer
> (as a more transactional oriented repository for user data and blog entries)
>
> Anyways, I'd like to contribute the review result within a few days. This
> will be a PDF document, like a basic compendium with my findings on Pebble
> 2.6.2 . Maybe it should be part of the project, but not sure where to
> uploaded to though
>
> regards,
>
> Petre Maierean
> http://www.linkedin.com/
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Pebble-user mailing list
> Pebble-user@...
> https://lists.sourceforge.net/lists/listinfo/pebble-user
>
>

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Petre Maierean]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi,
I am not really happy with the fact that most references to views (+JSP) are hardwired into associated actions. This compared to a definition file such as tiles-definition.xml is quite limiting. But that would not even be a big issue since fragments are used and maybe customizable. My real concern with that pattern is actually extending the web app by adding it more actions. The base 50 actions are a piece of cake to rewrite, but I'm ok with your approach though
 
JQuery vs YUI is a matter of taste. I think the former has a much broader developer base, so, one can find a lot of widgets ready to use
Not sure what would make the app slow with Hibernate. I've been using that library in commercial apps for years. Beside being transactional, it is acceptable fast (depending on the hardware the app is running on). When deploying an extended web app on the cloud, there will always be the concern of backups, and how data is accessed. File system may not always be an option (think about Amazon WS)

regards,

Petre 

---

From: James Roper <james@...>
To: Mailing list for Pebble weblog users <pebble-user@...>
Sent: Tue, June 14, 2011 6:17:01 PM
Subject: Re: [pebble-user] On Pebble design

Hi Peter,

I have considered moving to a new MVC framework for Pebble, but
haven't yet because I don't think there are any major gains to be had
from rewriting the 50 or so actions.  What exactly do you want to
customise?  In Pebble 2.6.x I've added the ability to plugin in
actions and views, have a look at
https://bitbucket.org/jroper/pebble-mobile-plugin to see how this can
be done.  Though it is hand rolled, the current MVC framework in
Pebble is incredibly fast and simple, it's one of the things that
contributes to the speed of Pebble starting up, and also ensures that
Pebbles size isn't massive.

I'm more of a Sitemesh fan than Tiles fan, Sitemesh allows some really
cool stuff especially when it comes to making things pluggable.

Moving to jQuery may be a good idea, I've had a chat with Olaf and he
has suggested YUI instead.  I'm not set on either one particularly.

I am definitely against moving to Hibernate, hibernate is slow and
overkill for Pebble, and will likely complicate Pebble setup, the
whole point of Pebble is for it to be lightweight and very quick to
setup and install.  Additionally, RDBMS is the wrong solution for
storage in a document oriented application like Pebble, a NoSQL
Document based solution would be much better, I am currently thinking
OrientDB as it is Java, lightweight, and embeddable.

Cheers,

James

On 15 June 2011 03:06, Petre Maierean <pgm66plus@...> wrote:

> Hello,
>
> I'm reviewing the current design of Pebble in order to customize its page
> template for personal use. Not sure about how many developers are still on
> this list. Just wandering how many of you would be interested in
> participating in an initiative to modify the presentation tier of the
> application to make it more flexible for customization
>
> I am thinking of replacing the current view and controller
> (DefaultHttpController + Actions + View) with Apache Struts + Tiles + Spring
> FW + JQuery.js. I would also add Hibernate for the model's persistence layer
> (as a more transactional oriented repository for user data and blog entries)
>
> Anyways, I'd like to contribute the review result within a few days. This
> will be a PDF document, like a basic compendium with my findings on Pebble
> 2.6.2 . Maybe it should be part of the project, but not sure where to
> uploaded to though
>
> regards,
>
> Petre Maierean

> http://www.linkedin.com/
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Pebble-user mailing list
> Pebble-user@...
> https://lists.sourceforge.net/lists/listinfo/pebble-user
>
>

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Weiqi Gao-2]

Petre,

Although not currently working on Pebble code, I'm a developer and one
of the early adopters of Pebble (since 2003 at 1.4).

I chose Pebble for its *simplicity* and *performance*:

   + super-snappy response time, both authoring and viewing;
   + intuitive flat file organization of blog entries;
   + a templating system that won't make my brain explode;
   + overall well-thought out architecture;
   + a small war file that feels light weight and *clean*;
   + no frivolous jars just for the sake of the developer's convenience.

With that in mind, I'd say Hibernate is entirely out of character for
Pebble.  So are Spring FW and Struts to a lesser extent.  jQuery and
Tiles might be OK.

I appreciate your enthusiasm about Pebble and your willingness to pay
attention to its code base.  However I feel that I should let my
(somewhat strong) feelings known on this list rather than seeing Pebble
drive in a direction opposite to where I wish it to be.  Understand that
this is not personal and is one user's opinion only.

Like always in matters such as this, the initiative belongs to those who
*do the work*, and I'll let the committers make the judgment call.

Regards,
--
Weiqi

On 06/14/2011 12:06 PM, Petre Maierean wrote:

> Hello,
>
> I'm reviewing the current design of Pebble in order to customize its
> page template for personal use. Not sure about how many developers are
> still on this list. Just wandering how many of you would be interested
> in participating in an initiative to modify the presentation tier of the
> application to make it more flexible for customization
>
> I am thinking of replacing the current view and controller
> (DefaultHttpController + Actions + View) with Apache Struts + Tiles +
> Spring FW + JQuery.js. I would also add Hibernate for the model's
> persistence layer (as a more transactional oriented repository for user
> data and blog entries)
>
> Anyways, I'd like to contribute the review result within a few days.
> This will be a PDF document, like a basic compendium with my findings on
> Pebble 2.6.2 . Maybe it should be part of the project, but not sure
> where to uploaded to though
>
> regards,
>
> Petre Maierean
> http://www.linkedin.com
> <http://www.linkedin.com/profile/view?id=143874&locale=en_US&trk=tab_pro>/

--
Weiqi Gao
weiqigao@...
http://www.weiqigao.com/blog/

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[geezenslaw]

And, switching to Hibernate would kill a guy like as I'm between servers
right now. My old pebble blog is still on the old box and I can't get a
new version of pebble up-and-running. I have used pebble for many years
without having to futz with much but now I'm facing problems migrating
to the newer pebble on the new repo I think it is on Atlassian/Jira
right? The original version of Pebble I have now came from (I believe)
Sourceforge.

Though I am struggling with migrating pebble to my new cloud slice I
suspect I will eventually get it done. but if the whole project changes
wholesale underneath me my blog entries since 2004 will disappear.

FWIW: I'm mostly a Grails developer now and my collaborator and I opted
out of YUI for JQuery. YUI early on seemed very slick but as the demands
went up YUI became unwieldly.

And, if anyone wanted to replace the hand-rolled MVC with a framework I
can easily suggest Grails if someone wanted to put in the time for
custom Grails GSP templates assuming the out-of-the-box templates are
not desirable.

Grails defaults to Hibernate but since Grails is very (very) plugin
oriented their are several NoSQL plugins for Grails that will replace
the Hibernate such as: MongoDB and another NoSQL I don't remember right
now.

my2cents.



On Tue, 2011-06-14 at 19:29 -0500, Weiqi Gao wrote:

> Petre,
>
> Although not currently working on Pebble code, I'm a developer and one
> of the early adopters of Pebble (since 2003 at 1.4).
>
> I chose Pebble for its *simplicity* and *performance*:
>
>    + super-snappy response time, both authoring and viewing;
>    + intuitive flat file organization of blog entries;
>    + a templating system that won't make my brain explode;
>    + overall well-thought out architecture;
>    + a small war file that feels light weight and *clean*;
>    + no frivolous jars just for the sake of the developer's convenience.
>
> With that in mind, I'd say Hibernate is entirely out of character for
> Pebble.  So are Spring FW and Struts to a lesser extent.  jQuery and
> Tiles might be OK.
>
> I appreciate your enthusiasm about Pebble and your willingness to pay
> attention to its code base.  However I feel that I should let my
> (somewhat strong) feelings known on this list rather than seeing Pebble
> drive in a direction opposite to where I wish it to be.  Understand that
> this is not personal and is one user's opinion only.
>
> Like always in matters such as this, the initiative belongs to those who
> *do the work*, and I'll let the committers make the judgment call.
>
> Regards,
> --
> Weiqi
>
> On 06/14/2011 12:06 PM, Petre Maierean wrote:
> > Hello,
> >
> > I'm reviewing the current design of Pebble in order to customize its
> > page template for personal use. Not sure about how many developers are
> > still on this list. Just wandering how many of you would be interested
> > in participating in an initiative to modify the presentation tier of the
> > application to make it more flexible for customization
> >
> > I am thinking of replacing the current view and controller
> > (DefaultHttpController + Actions + View) with Apache Struts + Tiles +
> > Spring FW + JQuery.js. I would also add Hibernate for the model's
> > persistence layer (as a more transactional oriented repository for user
> > data and blog entries)
> >
> > Anyways, I'd like to contribute the review result within a few days.
> > This will be a PDF document, like a basic compendium with my findings on
> > Pebble 2.6.2 . Maybe it should be part of the project, but not sure
> > where to uploaded to though
> >
> > regards,
> >
> > Petre Maierean
> > http://www.linkedin.com
> > <http://www.linkedin.com/profile/view?id=143874&locale=en_US&trk=tab_pro>/
>

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[James Roper-6]

Hi David,

If what problems are you having?  Only issue tracking and source code
have moved to JIRA Studio (http://open.jira.com/browse/PEBBLE), but
this has no impact on Pebble itself, and you should still be able to
get the latest Pebble binary from Sourceforge:

http://prdownloads.sourceforge.net/pebble/pebble-2.6.2.zip?download

Cheers,

James

On 15 June 2011 13:50, David Brown <david@...> wrote:

> And, switching to Hibernate would kill a guy like as I'm between servers
> right now. My old pebble blog is still on the old box and I can't get a
> new version of pebble up-and-running. I have used pebble for many years
> without having to futz with much but now I'm facing problems migrating
> to the newer pebble on the new repo I think it is on Atlassian/Jira
> right? The original version of Pebble I have now came from (I believe)
> Sourceforge.
>
> Though I am struggling with migrating pebble to my new cloud slice I
> suspect I will eventually get it done. but if the whole project changes
> wholesale underneath me my blog entries since 2004 will disappear.
>
> FWIW: I'm mostly a Grails developer now and my collaborator and I opted
> out of YUI for JQuery. YUI early on seemed very slick but as the demands
> went up YUI became unwieldly.
>
> And, if anyone wanted to replace the hand-rolled MVC with a framework I
> can easily suggest Grails if someone wanted to put in the time for
> custom Grails GSP templates assuming the out-of-the-box templates are
> not desirable.
>
> Grails defaults to Hibernate but since Grails is very (very) plugin
> oriented their are several NoSQL plugins for Grails that will replace
> the Hibernate such as: MongoDB and another NoSQL I don't remember right
> now.
>
> my2cents.
>
>
>
> On Tue, 2011-06-14 at 19:29 -0500, Weiqi Gao wrote:
>> Petre,
>>
>> Although not currently working on Pebble code, I'm a developer and one
>> of the early adopters of Pebble (since 2003 at 1.4).
>>
>> I chose Pebble for its *simplicity* and *performance*:
>>
>>    + super-snappy response time, both authoring and viewing;
>>    + intuitive flat file organization of blog entries;
>>    + a templating system that won't make my brain explode;
>>    + overall well-thought out architecture;
>>    + a small war file that feels light weight and *clean*;
>>    + no frivolous jars just for the sake of the developer's convenience.
>>
>> With that in mind, I'd say Hibernate is entirely out of character for
>> Pebble.  So are Spring FW and Struts to a lesser extent.  jQuery and
>> Tiles might be OK.
>>
>> I appreciate your enthusiasm about Pebble and your willingness to pay
>> attention to its code base.  However I feel that I should let my
>> (somewhat strong) feelings known on this list rather than seeing Pebble
>> drive in a direction opposite to where I wish it to be.  Understand that
>> this is not personal and is one user's opinion only.
>>
>> Like always in matters such as this, the initiative belongs to those who
>> *do the work*, and I'll let the committers make the judgment call.
>>
>> Regards,
>> --
>> Weiqi
>>
>> On 06/14/2011 12:06 PM, Petre Maierean wrote:
>> > Hello,
>> >
>> > I'm reviewing the current design of Pebble in order to customize its
>> > page template for personal use. Not sure about how many developers are
>> > still on this list. Just wandering how many of you would be interested
>> > in participating in an initiative to modify the presentation tier of the
>> > application to make it more flexible for customization
>> >
>> > I am thinking of replacing the current view and controller
>> > (DefaultHttpController + Actions + View) with Apache Struts + Tiles +
>> > Spring FW + JQuery.js. I would also add Hibernate for the model's
>> > persistence layer (as a more transactional oriented repository for user
>> > data and blog entries)
>> >
>> > Anyways, I'd like to contribute the review result within a few days.
>> > This will be a PDF document, like a basic compendium with my findings on
>> > Pebble 2.6.2 . Maybe it should be part of the project, but not sure
>> > where to uploaded to though
>> >
>> > regards,
>> >
>> > Petre Maierean
>> > http://www.linkedin.com
>> > <http://www.linkedin.com/profile/view?id=143874&locale=en_US&trk=tab_pro>/
>>
>
>
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Pebble-user mailing list
> Pebble-user@...
> https://lists.sourceforge.net/lists/listinfo/pebble-user
>

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[pieroxy-2]

Old time user here. Speaking for myself ;-)

Throwing half a dozen bloated libraries at pebble will most likely raise many more issues that it will solve. 

Those libraries are made for people that don't want to bother with coding this or that specific layer of architecture. They work fairly well but invariably add to the code base, to the memory consumption, to the CPU time, and to the global readability and maintenability. 

When you don't have time for these "petty layers" and have many other stuff to code on top of them, they're fine. 

In my view, Pebble is just not the right app for this. 

I'd eventually settle with jquery (even though it migh be the worst offender here) because ui layer is often something devs don't want to bother too much with - something to do with fragmentation and stuff. I should know, I am a ui Dev myself. 

My $0.02

Pierre

Le 14 juin 2011 à 19:06, Petre Maierean <pgm66plus@...> a écrit :

Hello,

I'm reviewing the current design of Pebble in order to customize its page template for personal use. Not sure about how many developers are still on this list. Just wandering how many of you would be interested in participating in an initiative to modify the presentation tier of the application to make it more flexible for customization

I am thinking of replacing the current view and controller (DefaultHttpController + Actions + View) with Apache Struts + Tiles + Spring FW + JQuery.js. I would also add Hibernate for the model's persistence layer (as a more transactional oriented repository for user data and blog entries)

Anyways, I'd like to contribute the review result within a few days. This will be a PDF document, like a basic compendium with my findings on Pebble 2.6.2 . Maybe it should be part of the project, but not sure where to uploaded to though

regards,

Petre Maierean
http://www.linkedin.com/

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev

_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Alan Burlison-2]

On 14/06/2011 23:58, Petre Maierean wrote:

> I am not really happy with the fact that most references to views (+JSP) are
> hardwired into associated actions. This compared to a definition file such as
> tiles-definition.xml is quite limiting. But that would not even be a big issue
> since fragments are used and maybe customizable. My real concern with that
> pattern is actually extending the web app by adding it more actions. The base 50
> actions are a piece of cake to rewrite, but I'm ok with your approach though
>
> JQuery vs YUI is a matter of taste. I think the former has a much broader
> developer base, so, one can find a lot of widgets ready to use
>
> Not sure what would make the app slow with Hibernate. I've been using that
> library in commercial apps for years. Beside being transactional, it is
> acceptable fast (depending on the hardware the app is running on). When
> deploying an extended web app on the cloud, there will always be the concern of
> backups, and how data is accessed. File system may not always be an option
> (think about Amazon WS)

If you want to fork Pebble to add all that (IMHO completely unnecessary)
goop, fine.  But please keep it out of pebble itself.

--
Alan Burlison
--

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Alan Burlison-2]

On 15/06/2011 01:29, Weiqi Gao wrote:

> I chose Pebble for its *simplicity* and *performance*:
>
>     + super-snappy response time, both authoring and viewing;
>     + intuitive flat file organization of blog entries;
>     + a templating system that won't make my brain explode;
>     + overall well-thought out architecture;
>     + a small war file that feels light weight and *clean*;
>     + no frivolous jars just for the sake of the developer's convenience.
>
> With that in mind, I'd say Hibernate is entirely out of character for
> Pebble.  So are Spring FW and Struts to a lesser extent.  jQuery and
> Tiles might be OK.

A big, fat +1.

--
Alan Burlison
--

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Jeff-349]

I, for one (well, ok, two) add my own big fat +1 to this.

>---- Original Message ----
>From: Alan Burlison <alan.burlison@...>
>To: "Mailing list for Pebble weblog users" <pebble-user@...>
>Cc: "Weiqi Gao" <weiqigao@...>
>Sent: Thu, Jun 16, 2011, 6:08 AM
>Subject: Re: [pebble-user] On Pebble design
>
>On 15/06/2011 01:29, Weiqi Gao wrote:
>
>> I chose Pebble for its *simplicity* and *performance*:
>>
>>     + super-snappy response time, both authoring and viewing;
>>     + intuitive flat file organization of blog entries;
>>     + a templating system that won't make my brain explode;
>>     + overall well-thought out architecture;
>>     + a small war file that feels light weight and *clean*;
>>     + no frivolous jars just for the sake of the developer's convenience.
>>
>> With that in mind, I'd say Hibernate is entirely out of character for
>> Pebble.  So are Spring FW and Struts to a lesser extent.  jQuery and
>> Tiles might be OK.
>
>A big, fat +1.
>
>--
>Alan Burlison
>--
>
>------------------------------------------------------------------------------
>EditLive Enterprise is the world's most technically advanced content
>authoring tool. Experience the power of Track Changes, Inline Image
>Editing and ensure content is compliant with Accessibility Checking.
>http://p.sf.net/sfu/ephox-dev2dev
>_______________________________________________
>Pebble-user mailing list
>Pebble-user@...
>https://lists.sourceforge.net/lists/listinfo/pebble-user

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Jeff-349]

While I would like a bit better templating, I have found that I can create my own custom template fairly easily.  Probably my largest complaint is that I can't seem to make another "module" yet  - probably because I've only spent maybe 45 minutes trying so far because work and other parts of life have been extremely busy.  I've tried starting with one of the existing "modules" (I'm away from access to it right now so I'm not sure I'm calling it the right thing) and going from there, but I get errors.  I'd like to be able to enclose weather data, or some other information.  Once I figure it out, I'm probably going to write a "How-to" for those that follow.  Then, hopefully, it will be as simple as taking the "module" template and putting your own "stuff" inside it, following a few rules.

As far as I can tell it should be easy in pebble to do this, but as I mentioned, I haven't had enough time to devote to it.

I'd agree with forking the repository, but at some point it should be determined if the fork should be integrated to the whole, or set off on it's own.

Just my own $0.02, which along with a quarter still won't by a cup of coffee these days

>---- Original Message ----
>From: Alan Burlison <alan.burlison@...>
>To: "Mailing list for Pebble weblog users" <pebble-user@...>
>Sent: Thu, Jun 16, 2011, 6:08 AM
>Subject: Re: [pebble-user] On Pebble design
>
>On 14/06/2011 23:58, Petre Maierean wrote:
>
>> I am not really happy with the fact that most references to views (+JSP) are
>> hardwired into associated actions. This compared to a definition file such as
>> tiles-definition.xml is quite limiting. But that would not even be a big issue
>> since fragments are used and maybe customizable. My real concern with that
>> pattern is actually extending the web app by adding it more actions. The base 50
>> actions are a piece of cake to rewrite, but I'm ok with your approach though
>>
>> JQuery vs YUI is a matter of taste. I think the former has a much broader
>> developer base, so, one can find a lot of widgets ready to use
>>
>> Not sure what would make the app slow with Hibernate. I've been using that
>> library in commercial apps for years. Beside being transactional, it is
>> acceptable fast (depending on the hardware the app is running on). When
>> deploying an extended web app on the cloud, there will always be the concern of
>> backups, and how data is accessed. File system may not always be an option
>> (think about Amazon WS)
>
>If you want to fork Pebble to add all that (IMHO completely unnecessary)
>goop, fine.  But please keep it out of pebble itself.
>
>--
>Alan Burlison
>--
>
>------------------------------------------------------------------------------
>EditLive Enterprise is the world's most technically advanced content
>authoring tool. Experience the power of Track Changes, Inline Image
>Editing and ensure content is compliant with Accessibility Checking.
>http://p.sf.net/sfu/ephox-dev2dev
>_______________________________________________
>Pebble-user mailing list
>Pebble-user@...
>https://lists.sourceforge.net/lists/listinfo/pebble-user

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user

[Olaf Kock-3]

Hi all,

back from travel I'm slowly catching up on mail before I leave again...
my 0.02€:

I chose pebble because of the simple infrastructure requirement (e.g.
store files) - had I wanted more, I would have chosen a different platform.

As you've seen, James has driven the development of new features as well
as bugfixing (a big thank you for that) since I barely found time to
continue working on this project. Plus, I'm extremely happy that he took
over.

With that, I would put my words behind whatever James' decision is.
Personally I don't know why we'd change something to a different library
"just because". If there's no specific value, I don't think the
architecture should be totally worked over, and if it would be, struts
would probably not be my first choice. When significant work is
invested, something new should come out, not just the same on a
different implementation. Changing the persistence as well as the view
layers of pebble would IMHO mean starting over and will result in a
completely new product.

If there is value (or something pluggable) in a different implementation
for one layer, it'd probably be possible to include it as a configurable
option into pebble, but please keep the current simplicity and
infrastructure requirements in mind. Otherwise one of the other
available implementations might be a better place to start - I'd almost
expect them to already have a database backend and a templating engine
on presentation layer, but it's been a long time that I even cared.

 From my work background though, I can't resist to suggest taking a look
on Liferay - ok, it's a full portal, but there's a blog portlet
available. Complexity-wise this is a completely different world than
pebble though. But there's struts as well as hibernate and templating
engines in there ;-)

Olaf

On 15.06.2011 06:00, James Roper wrote:

> Hi David,
>
> If what problems are you having?  Only issue tracking and source code
> have moved to JIRA Studio (http://open.jira.com/browse/PEBBLE), but
> this has no impact on Pebble itself, and you should still be able to
> get the latest Pebble binary from Sourceforge:
>
> http://prdownloads.sourceforge.net/pebble/pebble-2.6.2.zip?download
>
> Cheers,
>
> James
>
> On 15 June 2011 13:50, David Brown<david@...>  wrote:
>> And, switching to Hibernate would kill a guy like as I'm between servers
>> right now. My old pebble blog is still on the old box and I can't get a
>> new version of pebble up-and-running. I have used pebble for many years
>> without having to futz with much but now I'm facing problems migrating
>> to the newer pebble on the new repo I think it is on Atlassian/Jira
>> right? The original version of Pebble I have now came from (I believe)
>> Sourceforge.
>>
>> Though I am struggling with migrating pebble to my new cloud slice I
>> suspect I will eventually get it done. but if the whole project changes
>> wholesale underneath me my blog entries since 2004 will disappear.
>>
>> FWIW: I'm mostly a Grails developer now and my collaborator and I opted
>> out of YUI for JQuery. YUI early on seemed very slick but as the demands
>> went up YUI became unwieldly.
>>
>> And, if anyone wanted to replace the hand-rolled MVC with a framework I
>> can easily suggest Grails if someone wanted to put in the time for
>> custom Grails GSP templates assuming the out-of-the-box templates are
>> not desirable.
>>
>> Grails defaults to Hibernate but since Grails is very (very) plugin
>> oriented their are several NoSQL plugins for Grails that will replace
>> the Hibernate such as: MongoDB and another NoSQL I don't remember right
>> now.
>>
>> my2cents.
>>
>>
>>
>> On Tue, 2011-06-14 at 19:29 -0500, Weiqi Gao wrote:
>>> Petre,
>>>
>>> Although not currently working on Pebble code, I'm a developer and one
>>> of the early adopters of Pebble (since 2003 at 1.4).
>>>
>>> I chose Pebble for its *simplicity* and *performance*:
>>>
>>>     + super-snappy response time, both authoring and viewing;
>>>     + intuitive flat file organization of blog entries;
>>>     + a templating system that won't make my brain explode;
>>>     + overall well-thought out architecture;
>>>     + a small war file that feels light weight and *clean*;
>>>     + no frivolous jars just for the sake of the developer's convenience.
>>>
>>> With that in mind, I'd say Hibernate is entirely out of character for
>>> Pebble.  So are Spring FW and Struts to a lesser extent.  jQuery and
>>> Tiles might be OK.
>>>
>>> I appreciate your enthusiasm about Pebble and your willingness to pay
>>> attention to its code base.  However I feel that I should let my
>>> (somewhat strong) feelings known on this list rather than seeing Pebble
>>> drive in a direction opposite to where I wish it to be.  Understand that
>>> this is not personal and is one user's opinion only.
>>>
>>> Like always in matters such as this, the initiative belongs to those who
>>> *do the work*, and I'll let the committers make the judgment call.
>>>
>>> Regards,
>>> --
>>> Weiqi
>>>
>>> On 06/14/2011 12:06 PM, Petre Maierean wrote:
>>>> Hello,
>>>>
>>>> I'm reviewing the current design of Pebble in order to customize its
>>>> page template for personal use. Not sure about how many developers are
>>>> still on this list. Just wandering how many of you would be interested
>>>> in participating in an initiative to modify the presentation tier of the
>>>> application to make it more flexible for customization
>>>>
>>>> I am thinking of replacing the current view and controller
>>>> (DefaultHttpController + Actions + View) with Apache Struts + Tiles +
>>>> Spring FW + JQuery.js. I would also add Hibernate for the model's
>>>> persistence layer (as a more transactional oriented repository for user
>>>> data and blog entries)
>>>>
>>>> Anyways, I'd like to contribute the review result within a few days.
>>>> This will be a PDF document, like a basic compendium with my findings on
>>>> Pebble 2.6.2 . Maybe it should be part of the project, but not sure
>>>> where to uploaded to though
>>>>
>>>> regards,
>>>>
>>>> Petre Maierean
>>>> http://www.linkedin.com
>>>> <http://www.linkedin.com/profile/view?id=143874&locale=en_US&trk=tab_pro>/

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Pebble-user mailing list
Pebble-user@...
https://lists.sourceforge.net/lists/listinfo/pebble-user