[Building Sakai] Portal NEO Prefix

[David Adams]

+1

I don't see how fixing this would interfere with Chuck's plans for
future elimination of technical debt. This *is* technical debt in
addition to being a source of bugs and confusion.

-dave

Aaron Zeckoski wrote:
> Right, I think the suggestion is really just:
> 1) Get rid of the odd neo prefix stuff (which some tools do not even support)
> 2) Make the neo portal the default and allow people to swap back if
> they don't want it by adding in some config(s)
>
> So the real question is, are those 2 things harder than making the
> tools which are not "neo aware" work correctly and dealing with the
> community confusion through the 2.9 lifecycle.
>
> -AZ
>
>
> On Sat, Mar 16, 2013 at 7:47 AM, Steve Swinsburg
> <steve.swinsburg at gmail.com> wrote:
> > Wouldn't it make more sense to have people setting the portal to the old
> > templates if they want that, and then a skin to suit? That is exactly what I
> > do now for some installs sonce they h e majorly complex skins and migrating
> > is not an option yet.
> >
> > Having a prefix automatically added is a bit confusing.
> >
> > Sure the old skin is called default and the new one neo-default but I think
> > that's ok if documented.
> >
> > Definitely do not remove old skins or merge them, I didn't think that was
> > suggested at all? Just the prefix addition in the portal.
> >
> > So if people want old portal:
> >
> > Portal.templates=defaultskin (or whatever that value is)
> > Skin.default=some28compatibleskin
> >
> > If people want current portal, which is default, they just set the skin they
> > want, or use the neo-default.
> >
> > Skin.default=some29compatibleskin
> >
> >
> > Cheers
> > Steve
> >
> >
> >
> > Sent from my iPhone
> >
> > On 16/03/2013, at 15:24, Charles Severance <csev at umich.edu> wrote:
> >
> > Woah.  Not so fast.  Not so fast.
> >
> > Great care was taken to make sure schools could switch back and forth
> > between the old skin and the new skin.   So everything for the old skin is
> > left 100% intact and untouched form 2.8.
> >
> > I agree that by now, there is little value in going to 2.9 and using the old
> > skin.
> >
> > But I don't think that there is an easy way to transition unless we
> > completely wipe out the old skin - if we start sliding new things into the
> > old places we will break the ability to go back.  We need to fix it all -
> > not slide little things back and forth.
> >
> > It was my intention after 2.9.2 was released and delete the old skin from
> > trunk and make neo the only skin and I was going to remove cruft like the
> > frameset portal and generally reduce some technical debt in portal.
> >
> > But (there always is a but) this needs to be done all in a nice big change
> > and then heavily tested.
> >
> > I don't think that it is possible at all to make this into 2.9.2 - but I
> > would think we could do this in trunk shortly after we release 2.9.2 and
> > then we would end up with several months of developer testing after the
> > change is made.
> >
> > I was going to spend some time on this early summer as part of my quest to
> > reduce technical debt.
> >
> > So I would hold off quick hacks until we come up with a good way to really
> > do this right.
> >
> > Make sense?
> >
> > /Chuck
> >
> > On Mar 15, 2013, at 1:40 PM, Sam Ottenhoff wrote:
> >
> > Can someone explain the need for the 2.9+ property called portal.neoprefix
> > with a default value of "neo-"?  I understand that it means your "default"
> > skin now becomes "neo-default", but why was it needed?
> >
> > We are starting to see some requests like this one:
> >
> >   https://jira.sakaiproject.org/browse/STAT-345
> >
> > The tools include a link to the tool.css file, but it's not the one they
> > expect because the tool has no idea about this neoprefix.
> >
> > So, is neoprefix necessary?  Do we need to patch the tools to make them
> > neo-aware?
> >
> > Thanks,
> > Sam
> > _______________________________________________
> > sakai-dev mailing list
> > sakai-dev at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> > with a subject of "unsubscribe"
> >
> >
> > _______________________________________________
> > sakai-dev mailing list
> > sakai-dev at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> > with a subject of "unsubscribe"
> >
> >
> > _______________________________________________
> > sakai-dev mailing list
> > sakai-dev at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> > with a subject of "unsubscribe"
>