Doug Turner (:dougt) Assignee
	Description • 17 years ago

we need to move mobile components out of mozilla/minimo and move them into mozilla/extensions

The list is:

minimo/components/gps   --> extensions/gps
minimo/components/phone   --> extensions/phone
minimo/components/softkb   --> extensions/softkb
minimo/components/ssr   --> extensions/ssr
minimo/components/ssl   --> extensions/schannel_ssl

	Benjamin Smedberg
	Comment 1 • 17 years ago

I am not a fan of extensions/ at all... most of the stuff that lives there shouldn't... in addition, I don't think we should be moving anything in CVS. Any filesystem changes should occur in mercurial where moves are recorded reasonably.

I'd propose mozilla/mobile/gps etc so that we organize the source tree by function.

	Doug Turner (:dougt) Assignee
	Comment 2 • 17 years ago

happy to move into HG.  maybe this is the right time.  where in hg would this stuff live -- maybe just in its own repo?

why would gps be specific to mobile -- you can easily tether a BT GPS on a notebook.

	Benjamin Smedberg
	Comment 3 • 17 years ago

It's not necessarily specific to mobile, but that seems like a good place for it; other theoretical clients can build it from that location.

If you want an Hg repository which is just the mobile frontend stuff that's easy to arrange... we can arrange for that tree to be checked out in a subdirectory of mozilla-central for a unified build (much like js/tamarin is now).

I'm mainly concerned to avoid tree reorganizations in CVS because it represents move history so poorly.

	Doug Turner (:dougt) Assignee
	Comment 4 • 17 years ago

I would like to share some these things (gps, maybe softkey) with non-mobile things, so being non-mobile-branded is important.  And of course, these extensions are not browser specific either.

	Brad Lassey [:blassey] (use needinfo?)
	Comment 5 • 17 years ago

I'm working on enabling the soft keyboard for browser builds on maemo now.  I think this and most of these belong in extensions,  to remove their "mobile" tag, to share them across applications and to eliminate the need to hack a conditional into browser/allmakefiles.sh 

	Doug Turner (:dougt) Assignee
	Comment 6 • 17 years ago

working with roc and the widget peers to move softkey stuff into widget.  Most of the code will move under widget just fine.  However, we need a place for software keyboard implemented in xul.  Would toolkit be the right place for something like this benjamin?

	Stuart Parmenter
	Comment 7 • 17 years ago

bsmedberg: putting these things under mobile/ doesn't make sense for all of the things above.  we should probably move these on an individual basis as all of them will need to be code reviewed upon being moved in to the main tree.

soft keyboard is probably the first thing

	Doug Turner (:dougt) Assignee
	Comment 8 • 17 years ago

We are doing these migration on a case-by-case basis.  Marking wontfix since we will follow up with separate bugs for each required mobile-component-move..

	Reed Loden [:reed]
	Comment 9 • 17 years ago

(In reply to comment #8)
> We are doing these migration on a case-by-case basis.  Marking wontfix since we
> will follow up with separate bugs for each required mobile-component-move..

Can't this be a meta bug?

	Doug Turner (:dougt) Assignee
	Comment 10 • 17 years ago

sure, it can be a meta bug.  do you need a meta bug,  I do not think I do.... maybe brad does?

	Brad Lassey [:blassey] (use needinfo?)
	Comment 11 • 17 years ago

I don't necessarily need a meta bug, but we should make sure everything gets triaged.