You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Team Vit <te...@gmail.com> on 2007/04/22 07:03:13 UTC
Modifying the Jetspeed Desktop
Hi there,
I would like to completely change the web interface of the AJAX desktop,
by dropping dojo, and the layouts concepts. If I had to do so, How would i
go about it
Could Someone please guide me here as to where to start???
Also, if i had to disable the /portal view, how would i do it??
Regards
Team VIT
Re: Modifying the Jetspeed Desktop
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Apr 22, 2007, at 7:03 AM, Team Vit wrote:
> Hi there,
>
> I would like to completely change the web interface of the AJAX
> desktop,
> by dropping dojo, and the layouts concepts. If I had to do so, How
> would i
> go about it
I think you would first have to have a good understanding of the code
I would start reviewing the code, maybe taking it through the
debugger, walking thru it
Also have a look at the /desktop pipeline, and then the desktop
javascript code
> Could Someone please guide me here as to where to start???
> Also, if i had to disable the /portal view, how would i do it??
>
Remove the /portal entry from the mapping in the Spring configuration
file pipelines.xml:
<bean id='pipeline-map'
class='java.util.HashMap'>
<constructor-arg>
<map>
<entry key='/portlet'>
<value>portlet-pipeline</value>
</entry>
<entry key='/portal'>
<value>jetspeed-pipeline</value>
</entry>
Also remove the pipeline itself :
<bean id="jetspeed-pipeline"
class="org.apache.jetspeed.pipeline.JetspeedPipeline"
init-method="initialize"
>
Re: Modifying the Jetspeed Desktop
Posted by Team Vit <te...@gmail.com>.
hi david,
Sorry, what i meant was about the concept of decorators , layouts and theme
which according to me, might be easier if there was one concept as scott
suggested,
I was not referring to the PSML pages
I will see if there is any way I can work around this or
> possibly get a screen cam of it in action.
>
> That would be really great,
Thanks
Team Vit
On 4/25/07, David Sean Taylor <da...@bluesunrise.com> wrote:
>
>
> On Apr 24, 2007, at 8:40 PM, Team Vit wrote:
>
> > hi there,
> >
> > well scott, what you have done is similar to what i am planning to do
> > since personally i think it is easier for the designer to design if
> > he has
> > to change the look at one single page ( approx) .
>
> I would like to point out that the Jetspeed Desktop is also based on
> one single page
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
Re: Modifying the Jetspeed Desktop
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Apr 24, 2007, at 8:40 PM, Team Vit wrote:
> hi there,
>
> well scott, what you have done is similar to what i am planning to do
> since personally i think it is easier for the designer to design if
> he has
> to change the look at one single page ( approx) .
I would like to point out that the Jetspeed Desktop is also based on
one single page
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: Modifying the Jetspeed Desktop
Posted by "Weaver, Scott" <we...@ugs.com>.
Hi Team,
Performance was one of my top goals when I rewrote things. Our partner
portal site is accessed world wide so we had to make sure things were as
fast as possible (we will soon be implementing Akami services to
increase performance even more). My front page, on average, loads in
about 4-6 seconds regardless of the number of portlets. I have JSLINTed
(http://www.jslint.com/) and compressed all my javascript using the same
compressor that jQuery uses (which is FAR more aggressive than DOJO's
which is why you need to make sure all your javascript is LINTed before
hand). I also combine all my javascript files at build time into a
single file to reduce roundtrips. This really helps for regions that
have high latency levels.
I would love to have you show you the portal. Unfortunately it has
access to competitive information that cannot be exposed to the general
public. I will see if there is any way I can work around this or
possibly get a screen cam of it in action.
Regards,
-scott
> -----Original Message-----
> From: Team Vit [mailto:team.vit@gmail.com]
> Sent: Tuesday, April 24, 2007 2:41 PM
> To: Jetspeed Developers List
> Subject: Re: Modifying the Jetspeed Desktop
>
> hi there,
>
> well scott, what you have done is similar to what i am planning to do
> since personally i think it is easier for the designer to design if he
has
> to change the look at one single page ( approx) .
> I was thinking of not using any widgets at all for the rendering
> ...instead
> go with prototype
> for the ajax and simple anims. I haven't gone much deeply into
jQuery
> but
> from what i have seen it seems to be a much better alternative.
>
> My intention is to make an interface which is clean, simple and really
> fast
> ( responsive) .
> If you don't mind, and if it is not confidential , can we have a look
at
> what you have done with ur portal.
> especially the part about dropping layouts and decorators
> it will really be helpful to get a reference point for me to begin
with.
>
> I will be working on this as soon as my exams get over possible ...i.e
in
> about 20-30 days more.
> Hope fully i could make something good enuf to share it with you guys.
>
> Maybe we need to have a Jetspeed Summit meeting to discuss all these
> > new directions. like jQuery
> > I think it would be great to get you and Steve and Team and the
> > other /desktop developers together to brainstorm ....
> >
>
> I would love to be a part of this. I hope this can be done online .
>
> I think you would first have to have a good understanding of the code
> > I would start reviewing the code, maybe taking it through the
> > debugger, walking thru it
> > Also have a look at the /desktop pipeline, and then the desktop
> > javascript code
>
> will do .. and thanks for the help
>
> Regards
> Team Vit
>
>
>
>
>
>
>
> On 4/23/07, Weaver, Scott <we...@ugs.com> wrote:
> >
> > Hi Team,
> >
> > I am just curious. Which, if any, javascript API, are you thinking
of
> > replacing DOJO with? I was using DOJO for my "desktop"
implementation
> > but dropped it about 5 months ago because issues with size, relative
> > complexity, the dearth of documentation and performance issues
> > (specifically with widgets). I did a little research and decided to
go
> > with jQuery, which I immediately fell in love with. Compressed, the
> > base jQuery is only 19k.
> >
> > As for layouts, that is something I also replaced. What I came up
with
> > is based loosely on other CMS theme implementations (like that used
in
> > Drupal). It still uses Velocity as the templating language. I also
> > dropped the idea of separation of layouts from decorations. For me
it
> > was just over kill and was harder to manage than I would like. Now
you
> > just create a page.html in your theme directory and go from there.
> >
> > I would love to get my theme implementation back into Jetspeed 2 as
an
> > alternate to the layout approach. Unfortunately, I haven't had any
time
> > to pull down the newest J2 and get all the functionality (I don't
think
> > I currently support everything that the layouts do) in place in the
> > theme system.
> >
> > As for disabling /portal, I think that is as simple as removing the
> > servlet mapping from J2's web.xml.
> >
> > -scott
> >
> > > -----Original Message-----
> > > From: Team Vit [mailto:team.vit@gmail.com]
> > > Sent: Sunday, April 22, 2007 1:03 AM
> > > To: Jetspeed Users List; Jetspeed Developers List
> > > Subject: Modifying the Jetspeed Desktop
> > >
> > > Hi there,
> > >
> > > I would like to completely change the web interface of the AJAX
> > desktop,
> > > by dropping dojo, and the layouts concepts. If I had to do so, How
> > would i
> > > go about it
> > > Could Someone please guide me here as to where to start???
> > > Also, if i had to disable the /portal view, how would i do it??
> > >
> > >
> > > Regards
> > >
> > > Team VIT
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
jetspeed-dev-help@portals.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Modifying the Jetspeed Desktop
Posted by Team Vit <te...@gmail.com>.
hi there,
well scott, what you have done is similar to what i am planning to do
since personally i think it is easier for the designer to design if he has
to change the look at one single page ( approx) .
I was thinking of not using any widgets at all for the rendering ...instead
go with prototype
for the ajax and simple anims. I haven't gone much deeply into jQuery but
from what i have seen it seems to be a much better alternative.
My intention is to make an interface which is clean, simple and really fast
( responsive) .
If you don't mind, and if it is not confidential , can we have a look at
what you have done with ur portal.
especially the part about dropping layouts and decorators
it will really be helpful to get a reference point for me to begin with.
I will be working on this as soon as my exams get over possible ...i.e in
about 20-30 days more.
Hope fully i could make something good enuf to share it with you guys.
Maybe we need to have a Jetspeed Summit meeting to discuss all these
> new directions. like jQuery
> I think it would be great to get you and Steve and Team and the
> other /desktop developers together to brainstorm ....
>
I would love to be a part of this. I hope this can be done online .
I think you would first have to have a good understanding of the code
> I would start reviewing the code, maybe taking it through the
> debugger, walking thru it
> Also have a look at the /desktop pipeline, and then the desktop
> javascript code
will do .. and thanks for the help
Regards
Team Vit
On 4/23/07, Weaver, Scott <we...@ugs.com> wrote:
>
> Hi Team,
>
> I am just curious. Which, if any, javascript API, are you thinking of
> replacing DOJO with? I was using DOJO for my "desktop" implementation
> but dropped it about 5 months ago because issues with size, relative
> complexity, the dearth of documentation and performance issues
> (specifically with widgets). I did a little research and decided to go
> with jQuery, which I immediately fell in love with. Compressed, the
> base jQuery is only 19k.
>
> As for layouts, that is something I also replaced. What I came up with
> is based loosely on other CMS theme implementations (like that used in
> Drupal). It still uses Velocity as the templating language. I also
> dropped the idea of separation of layouts from decorations. For me it
> was just over kill and was harder to manage than I would like. Now you
> just create a page.html in your theme directory and go from there.
>
> I would love to get my theme implementation back into Jetspeed 2 as an
> alternate to the layout approach. Unfortunately, I haven't had any time
> to pull down the newest J2 and get all the functionality (I don't think
> I currently support everything that the layouts do) in place in the
> theme system.
>
> As for disabling /portal, I think that is as simple as removing the
> servlet mapping from J2's web.xml.
>
> -scott
>
> > -----Original Message-----
> > From: Team Vit [mailto:team.vit@gmail.com]
> > Sent: Sunday, April 22, 2007 1:03 AM
> > To: Jetspeed Users List; Jetspeed Developers List
> > Subject: Modifying the Jetspeed Desktop
> >
> > Hi there,
> >
> > I would like to completely change the web interface of the AJAX
> desktop,
> > by dropping dojo, and the layouts concepts. If I had to do so, How
> would i
> > go about it
> > Could Someone please guide me here as to where to start???
> > Also, if i had to disable the /portal view, how would i do it??
> >
> >
> > Regards
> >
> > Team VIT
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
Re: Modifying the Jetspeed Desktop
Posted by Aaron Evans <aa...@gmail.com>.
On 4/23/07, Weaver, Scott <we...@ugs.com> wrote:
> > I've been using dojo for a while now. In fact, I think it was a
> > posting from Scott that got me on to it!
>
> That's it blame me!!! LOL!
>
> I agree with you Aaron, I DETESTED writing my own javascript with all
> the browser crap that I had to keep in the back of my head and what.
> Dojo did improve on my feeling about using javascript somewhat.
> However, when I found jQuery, it was like a whole new world opened up.
> I actually wanted to write javascript, well at least writing it the
> jQuery way ;-). jQuery uses XPath for traversing the DOM and is quite
> quick at it. jQuery's has a plugin architecture for extending the
> jQuery core which is surprisingly elegant and simple. I find myself
> writing much less code now that I am using jQuery. You will be amazed
> at what you can to in just 10 lines of jQuery. jQuery also has a very
> active community and a plethora of 3rd party plugins already available.
>
> I dunno jQuery just "feels" right if that makes sense. It is the same
> feeling I got when I started using Spring.
>
> Okay, I will get off my soap box now ;-)
I think I read a bit about jquery a while back and it sounds
interesting. IIRC, and correct me if I am wrong, but i thought it kind
of worked like:
1. give me all nodes of type X
2. Now apply the following styles and behaviors to that resulting node set.
>
> p.s.
>
> Actually one of our biggest performance hang-ups (after widgets) was the
> DOJO packaging system. IIRC, any time you "include" a package an
> XMLHttpRequest is issued to the server to grab the code. From what I
> have seen and I may be wrong, browsers do not cache XMLHttpRequests,
> well at least not without jumping through nasty hoops on the server side
> and even then I don't know if you can get the browser to cache.
>
You address this issue by creating a custom build so that it need not
do an http request for these resources because they would be built
into the dojo.js file. I think it will cache the .js files anyway,
but not the .html files for the widget templates.
Anyhow, like I said, I'm not necessarily advocating dojo over other
solutions. But I am so neck deep in it now that we'll probably stick
with it for the forseable future.
-aaron
> -scott
>
> > -----Original Message-----
> > From: Aaron Evans [mailto:aaronmevans@gmail.com]
> > Sent: Monday, April 23, 2007 11:11 AM
> > To: Jetspeed Developers List
> > Subject: Re: Modifying the Jetspeed Desktop
> >
> > I've been using dojo for a while now. In fact, I think it was a
> > posting from Scott that got me on to it!
> >
> > We're using a custom build for it so I am not sure that I'll be able
> > to easily merge my build with the one that is used for desktop, but I
> > haven't tried.
> >
> > I hear all those frustrations with dojo, but they claim they're going
> > to address a bunch of them and finally release a 1.0 soon. In any
> > event, if you guys ultimately decide to switch I don't think it would
> > really matter to me in the long run.
> >
> > My biggest problem has been with widgets. At this point, they should
> > only be used sparsely because they just kill page load time if you use
> > a bunch of them in a page. So I've started moving away from them and
> > only using them here and there.
> >
> > Wrt the "re-writing" of javascript to be more like Java that Scott
> > mentioned, maybe Scott is right and this leads to problems. However, I
> > can tell you that I HATED coding javascript until I started using
> > dojo's packaging model. But then again, most of my experience with
> > javascript was back in the days of HTML 1.0 when it really did suck.
> > There are a ton of things you can do now that I had no idea you could
> > do.
> >
> > Anyhow, just my 2 cents...
> >
> > On 4/23/07, David Sean Taylor <da...@bluesunrise.com> wrote:
> > >
> > > On Apr 23, 2007, at 4:07 PM, Weaver, Scott wrote:
> > >
> > > > Sounds good to me I would love to get back in the game as it were
> :)
> > >
> > > Yeah, what happened to you dude, did you go on a road trip with Ken
> > > Kesey or what ;-) ?
> > > OK ... I need to get creative and come up with a way to get us
> > > together for the big summit....
> > >
> > >
> > > > One of DOJO's biggest downfalls was their attempt to "rewrite" how
> > > > javascript works and trying to make it more "java-like". This
> just
> > > > compounds the complexity exponentially when coupled with the fact
> that
> > > > the documentation is so sparse.
> > > >
> > >
> > > Yeah, I must say my productivity was way done using this framework,
> > > frustration way up
> > > That said it does work nicely at times
> > >
> > > Be interested to see what Steve says when he gets back from
> vacation....
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Modifying the Jetspeed Desktop
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Apr 23, 2007, at 8:41 PM, Santiago Gala wrote:
> El lun, 23-04-2007 a las 11:27 -0400, Weaver, Scott escribió:
> (...)
>> I actually wanted to write javascript, well at least writing it the
>> jQuery way ;-). jQuery uses XPath for traversing the DOM and is quite
>> quick at it.
>
> Why not JSON ( www.json.org ) ? it is way simpler to handle, plus it
> does not require well-formed XML. Well-formedness was my killer in our
> first attempt at client-side aggregation.
>
> JSON is generated and parsed very easily, in java, ruby, python, perl,
> and, of course, javascript.
>
>
A number of the Jetspeed APIs are already available in JSON or XML
since 2.1
RE: Modifying the Jetspeed Desktop
Posted by Santiago Gala <sa...@gmail.com>.
El lun, 23-04-2007 a las 15:12 -0400, Weaver, Scott escribió:
> Santiago,
>
> Actually, I use JSON for all of my AJA(X) work. The XPath is just for
> manipulating the DOM of an existing page. I use a combination of
> jQuery's built-in JSON support along with JSONStringify
> (http://www.thomasfrank.se/json_stringify_revisited.html) for the
> front end and JSONLib (http://json-lib.sourceforge.net/) on the back
> end. In fact, I wrote a complete JSON-based customization pipeline
> for my J2 portal.
>
Cool, I thought it was for selection on the answers.
> However, you must be aware of the security concerns when using JSON.
> If not secured properly, you can leave your end-users and your
> application open to x-site scripting attacks as documented here,
> http://www.fortifysoftware.com/servlet/downloads/public/JavaScript_Hijacking.pdf
>
I'm aware, but using XML only hides that the possibility of such attacks
is there, only a bit more difficult to happen. :)
Regards
Santiago
> -scott
>
> > -----Original Message-----
> > From: Santiago Gala [mailto:santiago.gala@gmail.com] On Behalf Of Santiago
> > Gala
> > Sent: Monday, April 23, 2007 2:41 PM
> > To: Jetspeed Developers List
> > Subject: RE: Modifying the Jetspeed Desktop
> >
> > El lun, 23-04-2007 a las 11:27 -0400, Weaver, Scott escribió:
> > (...)
> > > I actually wanted to write javascript, well at least writing it the
> > > jQuery way ;-). jQuery uses XPath for traversing the DOM and is quite
> > > quick at it.
> >
> > Why not JSON ( www.json.org ) ? it is way simpler to handle, plus it
> > does not require well-formed XML. Well-formedness was my killer in our
> > first attempt at client-side aggregation.
> >
> > JSON is generated and parsed very easily, in java, ruby, python, perl,
> > and, of course, javascript.
> >
> > Regards
> > Santiago
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: Modifying the Jetspeed Desktop
Posted by "Weaver, Scott" <we...@ugs.com>.
Santiago,
Actually, I use JSON for all of my AJA(X) work. The XPath is just for manipulating the DOM of an existing page. I use a combination of jQuery's built-in JSON support along with JSONStringify (http://www.thomasfrank.se/json_stringify_revisited.html) for the front end and JSONLib (http://json-lib.sourceforge.net/) on the back end. In fact, I wrote a complete JSON-based customization pipeline for my J2 portal.
However, you must be aware of the security concerns when using JSON. If not secured properly, you can leave your end-users and your application open to x-site scripting attacks as documented here, http://www.fortifysoftware.com/servlet/downloads/public/JavaScript_Hijacking.pdf
-scott
> -----Original Message-----
> From: Santiago Gala [mailto:santiago.gala@gmail.com] On Behalf Of Santiago
> Gala
> Sent: Monday, April 23, 2007 2:41 PM
> To: Jetspeed Developers List
> Subject: RE: Modifying the Jetspeed Desktop
>
> El lun, 23-04-2007 a las 11:27 -0400, Weaver, Scott escribió:
> (...)
> > I actually wanted to write javascript, well at least writing it the
> > jQuery way ;-). jQuery uses XPath for traversing the DOM and is quite
> > quick at it.
>
> Why not JSON ( www.json.org ) ? it is way simpler to handle, plus it
> does not require well-formed XML. Well-formedness was my killer in our
> first attempt at client-side aggregation.
>
> JSON is generated and parsed very easily, in java, ruby, python, perl,
> and, of course, javascript.
>
> Regards
> Santiago
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: Modifying the Jetspeed Desktop
Posted by Santiago Gala <sg...@apache.org>.
El lun, 23-04-2007 a las 11:27 -0400, Weaver, Scott escribió:
(...)
> I actually wanted to write javascript, well at least writing it the
> jQuery way ;-). jQuery uses XPath for traversing the DOM and is quite
> quick at it.
Why not JSON ( www.json.org ) ? it is way simpler to handle, plus it
does not require well-formed XML. Well-formedness was my killer in our
first attempt at client-side aggregation.
JSON is generated and parsed very easily, in java, ruby, python, perl,
and, of course, javascript.
Regards
Santiago
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: Modifying the Jetspeed Desktop
Posted by "Weaver, Scott" <we...@ugs.com>.
> I've been using dojo for a while now. In fact, I think it was a
> posting from Scott that got me on to it!
That's it blame me!!! LOL!
I agree with you Aaron, I DETESTED writing my own javascript with all
the browser crap that I had to keep in the back of my head and what.
Dojo did improve on my feeling about using javascript somewhat.
However, when I found jQuery, it was like a whole new world opened up.
I actually wanted to write javascript, well at least writing it the
jQuery way ;-). jQuery uses XPath for traversing the DOM and is quite
quick at it. jQuery's has a plugin architecture for extending the
jQuery core which is surprisingly elegant and simple. I find myself
writing much less code now that I am using jQuery. You will be amazed
at what you can to in just 10 lines of jQuery. jQuery also has a very
active community and a plethora of 3rd party plugins already available.
I dunno jQuery just "feels" right if that makes sense. It is the same
feeling I got when I started using Spring.
Okay, I will get off my soap box now ;-)
p.s.
Actually one of our biggest performance hang-ups (after widgets) was the
DOJO packaging system. IIRC, any time you "include" a package an
XMLHttpRequest is issued to the server to grab the code. From what I
have seen and I may be wrong, browsers do not cache XMLHttpRequests,
well at least not without jumping through nasty hoops on the server side
and even then I don't know if you can get the browser to cache.
-scott
> -----Original Message-----
> From: Aaron Evans [mailto:aaronmevans@gmail.com]
> Sent: Monday, April 23, 2007 11:11 AM
> To: Jetspeed Developers List
> Subject: Re: Modifying the Jetspeed Desktop
>
> I've been using dojo for a while now. In fact, I think it was a
> posting from Scott that got me on to it!
>
> We're using a custom build for it so I am not sure that I'll be able
> to easily merge my build with the one that is used for desktop, but I
> haven't tried.
>
> I hear all those frustrations with dojo, but they claim they're going
> to address a bunch of them and finally release a 1.0 soon. In any
> event, if you guys ultimately decide to switch I don't think it would
> really matter to me in the long run.
>
> My biggest problem has been with widgets. At this point, they should
> only be used sparsely because they just kill page load time if you use
> a bunch of them in a page. So I've started moving away from them and
> only using them here and there.
>
> Wrt the "re-writing" of javascript to be more like Java that Scott
> mentioned, maybe Scott is right and this leads to problems. However, I
> can tell you that I HATED coding javascript until I started using
> dojo's packaging model. But then again, most of my experience with
> javascript was back in the days of HTML 1.0 when it really did suck.
> There are a ton of things you can do now that I had no idea you could
> do.
>
> Anyhow, just my 2 cents...
>
> On 4/23/07, David Sean Taylor <da...@bluesunrise.com> wrote:
> >
> > On Apr 23, 2007, at 4:07 PM, Weaver, Scott wrote:
> >
> > > Sounds good to me I would love to get back in the game as it were
:)
> >
> > Yeah, what happened to you dude, did you go on a road trip with Ken
> > Kesey or what ;-) ?
> > OK ... I need to get creative and come up with a way to get us
> > together for the big summit....
> >
> >
> > > One of DOJO's biggest downfalls was their attempt to "rewrite" how
> > > javascript works and trying to make it more "java-like". This
just
> > > compounds the complexity exponentially when coupled with the fact
that
> > > the documentation is so sparse.
> > >
> >
> > Yeah, I must say my productivity was way done using this framework,
> > frustration way up
> > That said it does work nicely at times
> >
> > Be interested to see what Steve says when he gets back from
vacation....
> >
> >
> >
> >
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Modifying the Jetspeed Desktop
Posted by Aaron Evans <aa...@gmail.com>.
I've been using dojo for a while now. In fact, I think it was a
posting from Scott that got me on to it!
We're using a custom build for it so I am not sure that I'll be able
to easily merge my build with the one that is used for desktop, but I
haven't tried.
I hear all those frustrations with dojo, but they claim they're going
to address a bunch of them and finally release a 1.0 soon. In any
event, if you guys ultimately decide to switch I don't think it would
really matter to me in the long run.
My biggest problem has been with widgets. At this point, they should
only be used sparsely because they just kill page load time if you use
a bunch of them in a page. So I've started moving away from them and
only using them here and there.
Wrt the "re-writing" of javascript to be more like Java that Scott
mentioned, maybe Scott is right and this leads to problems. However, I
can tell you that I HATED coding javascript until I started using
dojo's packaging model. But then again, most of my experience with
javascript was back in the days of HTML 1.0 when it really did suck.
There are a ton of things you can do now that I had no idea you could
do.
Anyhow, just my 2 cents...
On 4/23/07, David Sean Taylor <da...@bluesunrise.com> wrote:
>
> On Apr 23, 2007, at 4:07 PM, Weaver, Scott wrote:
>
> > Sounds good to me I would love to get back in the game as it were :)
>
> Yeah, what happened to you dude, did you go on a road trip with Ken
> Kesey or what ;-) ?
> OK ... I need to get creative and come up with a way to get us
> together for the big summit....
>
>
> > One of DOJO's biggest downfalls was their attempt to "rewrite" how
> > javascript works and trying to make it more "java-like". This just
> > compounds the complexity exponentially when coupled with the fact that
> > the documentation is so sparse.
> >
>
> Yeah, I must say my productivity was way done using this framework,
> frustration way up
> That said it does work nicely at times
>
> Be interested to see what Steve says when he gets back from vacation....
>
>
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Modifying the Jetspeed Desktop
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Apr 23, 2007, at 4:07 PM, Weaver, Scott wrote:
> Sounds good to me I would love to get back in the game as it were :)
Yeah, what happened to you dude, did you go on a road trip with Ken
Kesey or what ;-) ?
OK ... I need to get creative and come up with a way to get us
together for the big summit....
> One of DOJO's biggest downfalls was their attempt to "rewrite" how
> javascript works and trying to make it more "java-like". This just
> compounds the complexity exponentially when coupled with the fact that
> the documentation is so sparse.
>
Yeah, I must say my productivity was way done using this framework,
frustration way up
That said it does work nicely at times
Be interested to see what Steve says when he gets back from vacation....
RE: Modifying the Jetspeed Desktop
Posted by "Weaver, Scott" <we...@ugs.com>.
Sounds good to me I would love to get back in the game as it were :)
One of DOJO's biggest downfalls was their attempt to "rewrite" how
javascript works and trying to make it more "java-like". This just
compounds the complexity exponentially when coupled with the fact that
the documentation is so sparse.
-scott
> -----Original Message-----
> From: David Sean Taylor [mailto:david@bluesunrise.com]
> Sent: Monday, April 23, 2007 9:55 AM
> To: Jetspeed Developers List
> Subject: Re: Modifying the Jetspeed Desktop
>
>
> On Apr 23, 2007, at 3:46 PM, Weaver, Scott wrote:
>
> > Hi Team,
> >
> > I am just curious. Which, if any, javascript API, are you thinking
of
> > replacing DOJO with? I was using DOJO for my "desktop"
implementation
> > but dropped it about 5 months ago because issues with size, relative
> > complexity, the dearth of documentation and performance issues
> > (specifically with widgets). I did a little research and decided
> > to go
> > with jQuery, which I immediately fell in love with. Compressed, the
> > base jQuery is only 19k.
> >
> I hear you about the documentation, man I do suffer there ....
>
> Maybe we need to have a Jetspeed Summit meeting to discuss all these
> new directions. like jQuery
> I think it would be great to get you and Steve and Team and the
> other /desktop developers together to brainstorm ....
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Modifying the Jetspeed Desktop
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Apr 23, 2007, at 3:46 PM, Weaver, Scott wrote:
> Hi Team,
>
> I am just curious. Which, if any, javascript API, are you thinking of
> replacing DOJO with? I was using DOJO for my "desktop" implementation
> but dropped it about 5 months ago because issues with size, relative
> complexity, the dearth of documentation and performance issues
> (specifically with widgets). I did a little research and decided
> to go
> with jQuery, which I immediately fell in love with. Compressed, the
> base jQuery is only 19k.
>
I hear you about the documentation, man I do suffer there ....
Maybe we need to have a Jetspeed Summit meeting to discuss all these
new directions. like jQuery
I think it would be great to get you and Steve and Team and the
other /desktop developers together to brainstorm ....
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: Modifying the Jetspeed Desktop
Posted by "Weaver, Scott" <we...@ugs.com>.
Hi Team,
I am just curious. Which, if any, javascript API, are you thinking of
replacing DOJO with? I was using DOJO for my "desktop" implementation
but dropped it about 5 months ago because issues with size, relative
complexity, the dearth of documentation and performance issues
(specifically with widgets). I did a little research and decided to go
with jQuery, which I immediately fell in love with. Compressed, the
base jQuery is only 19k.
As for layouts, that is something I also replaced. What I came up with
is based loosely on other CMS theme implementations (like that used in
Drupal). It still uses Velocity as the templating language. I also
dropped the idea of separation of layouts from decorations. For me it
was just over kill and was harder to manage than I would like. Now you
just create a page.html in your theme directory and go from there.
I would love to get my theme implementation back into Jetspeed 2 as an
alternate to the layout approach. Unfortunately, I haven't had any time
to pull down the newest J2 and get all the functionality (I don't think
I currently support everything that the layouts do) in place in the
theme system.
As for disabling /portal, I think that is as simple as removing the
servlet mapping from J2's web.xml.
-scott
> -----Original Message-----
> From: Team Vit [mailto:team.vit@gmail.com]
> Sent: Sunday, April 22, 2007 1:03 AM
> To: Jetspeed Users List; Jetspeed Developers List
> Subject: Modifying the Jetspeed Desktop
>
> Hi there,
>
> I would like to completely change the web interface of the AJAX
desktop,
> by dropping dojo, and the layouts concepts. If I had to do so, How
would i
> go about it
> Could Someone please guide me here as to where to start???
> Also, if i had to disable the /portal view, how would i do it??
>
>
> Regards
>
> Team VIT
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org