Hi, Bergie and I had a little discussion on IRC today. 14:40 <tarjei> the admin UI situation is very bad IMHO 14:40 <bergie> agreed 14:41 <bergie> we should have only one admin UI 14:41 <bergie> in my view, it should be: 14:41 <bergie> 1) using standards-based XHTML+CSS to be lightweight 14:41 <bergie> 2) Utilize the MidCOM API 14:41 <tarjei> yes and we need a roadmap towards it. 14:42 <bergie> agreed 14:42 <bergie> so basically, we should make an mRFC together that would be the spec, 14:43 <tarjei> yes 14:43 <tarjei> We need to get the whole comunity around it 14:43 <tarjei> also, not one mRFC : 14:43 <tarjei> 1) pagebased midcom 14:44 <tarjei> 2) mRFC 15 14:44 <bergie> yeah, page-based midcom is something we need 14:44 <tarjei> 3) mRFC for Aegir migration (rcs handling f.x. 14:44 <tarjei> 4) mRFC for new styleditor 14:45 <bergie> Datamanager already uses NemeinRCS 14:45 <tarjei> 5) a new midgard component for handling raw objects 14:45 <bergie> "object browser" 14:45 <tarjei> yep 14:45 <tarjei> 6) propper imagepopup 14:45 <bergie> for hosts we probably don't really need admin UI as we can expand the site wizard 14:46 <bergie> so the main points of Aegir will be styles and groups 14:46 <bergie> regarding the image popup, http://www.midgard-project.org/community/development/mrfc/0017.html 14:46 <tarjei> 2 things: 14:46 <tarjei> 1. groups , doesn't the sitewizard handle it? 14:47 <bergie> no, it handles SGs 14:47 <tarjei> 1. wrt "the main points" you need to add pages and old topics/articles. 14:47 <bergie> styles and group/user management need specialized UIs, everything else can be handled through the "object browser" 14:47 <tarjei> true 14:48 <bergie> content is already handled through midcom.admin.content (AIS) 14:48 <tarjei> but we'll need a simple component handling old article trees 14:48 <bergie> object browser? 14:49 <bergie> I think it should be able to handle all Midgard data, both old classes and MgdSchema based ones 14:49 <tarjei> my idea was to make the migrational component loong before the objectbrowser. 14:50 <tarjei> mainly because I want the OB to be pagebased 14:50 <bergie> good point. the migration tool should be a wizard, I think 14:50 <bergie> the OB can simply be a component 14:50 <bergie> like everything in the new admin tool should be 14:50 <tarjei> yes 14:52 <tarjei> I'm thinking the migrational component is just a simple thing so the user sees the articletree in ais but that the "real" site is not run by midcom 14:52 <tarjei> so you could just style it properly and stick it in the /aegir sublocation and the user shouldn't see much of a difference. 14:53 <tarjei> there are just to many ways to skin a cat using aegir that we can mange to make a migration wizard. 14:53 <bergie> well, as I said, nnb2midcom should help 14:54 <tarjei> it might :) 14:55 <tarjei> we should have a chat on the phone someday. 14:58 <bergie> +1 14:59 <bergie> anyway, can you post this log to the aegir thread?
tor, 28,.04.2005 kl. 13.11 +0300, skrev Henri Bergius: > Tarjei Huse wrote: > > 2. Make a new "base content" component that handles topics that have noe > > defined component (for migration of existing data). > > Or how about making a content migration wizard based on my nnb2midcom > script? > http://www.nehmer.net/~bergie/nnb2midcom.txt > > Especially if people are used Tony's index article enabled Aegir > Sample Site, the data format is very close and you can keep > both MidCOMized and the old Aegir-style site running side-by-side. > > For example: > http://www.sentera.fi/en/ > http://www.sentera.fi/uusi/en/ > > > Tarjei > > /Bergie > -- Tarjei Huse <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
